home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
tri_bbs
/
ttn0492.zip
/
GUIDLINE.TTN
< prev
next >
Wrap
Text File
|
1992-04-03
|
10KB
|
235 lines
The TriTel Network Updated: 04/02/92
System Guidlines, Rules and Regulations
---------------------------------------
1. Administration
A. The TriTel Network, hereafter referred to as TTN or the
network, is a basis for the exchange of electronic mail
between bulletin board systems throughout the country.
B. TTN's main Hub is James Bond's Hideaway, hereafter referred
to as the Net Host, and is operated Randy Hunt, hereafter
referred to as the Net Administrator.
C. The Net Administrator has final say on anything relating to
anything that occurs within the net.
2. Acceptance into TTN
A. Although almost nobody will be turned down acceptance into
the network, the Net Administrator does reserve the right to
deny anyone access to TTN, for any reason.
B. To be accepted, you must:
1. read these guidlines and agree to them.
2. completely fill out and sign and date the application
and mail it (via U.S. Mail, -NOT- E-Mail!) to the Net
Administrator.
3. be running TriTel
4. use the TriNet software, in conjunction with TriMail
only! (I.E. No FrontDoor, PCRelay, etc, etc)
5. carry a certain number of conferences, covered in
section 5.A
3. Net Administrator
A. The Net Administrator (N.A. for short), charges nothing for
TTN Hubs or Nodes to carry TTN.
B. The N.A. and the N.A's BBS shall be free of any and all claims
against the N.A., the N.A's BBS or TTN, or the operation of TTN.
C. The N.A., at any time, can take down TTN for ANY reason, for
any period of time. Theres no saying how long TTN will be in
operation, but hopefully it will be around for years to come.
D. The N.A. will have scheduled times for Hubs to poll (exchange
messages with) the N.A's BBS for mail. Nobody is to call outside
of these hours, if it is within another persons alloted time slot.
E. Never, EVER, ==EVER== call the N.A. via a voice line, without
first having permission to do so from the N.A. To quote Mark
Goodwin "My private life is just that--PRIVATE!".
F. The N.A. has the power to override any rules and regulations
as he sees fit.
G. The N.A. has the right to append, modify or delete any of these
guidelines, as described in section 9.A
4. Network Sysops Responsibilities and Duties
A. Hubs are required to relay mail a minimum of once a day with
the Net Host, unless it is completely impossible or unavoidable.
If a Hub does not make a successful relay for a period of seven
(7) straight days, they may be subject to temporary or permanent
expulsion from TTN.
B. Hubs must carry all required TTN conferences, as described in
section 5.A.
C. Hubs are responsible for helping all new nodes to get set up,
and they are responsible for assigning that node a time to do
a relay with said Hub.
D. Hubs may be asked to perform special functions, such as contact
nodes for the N.A, if a local call.
E. Although I do not encourage it at all, Hubs MAY charge nodes
a fee to carry conferences within TTN, for phone costs. This
fee must be the cost of the Hub to relay TTN, divided up
EQUALLY by all nodes, INCLUDING the Hub. I.E:
Fee=(cost of hub)/(total # of nodes, including hub)
F. If the hub runs a "pay BBS", the hub MUST provide a FREE account
on the hubs BBS for mail relays by any node that has been
assigned by the N.A. to that Hub.
G. Node Assignments
1. Hubs must allow new nodes to relay though them
as stated by the N.A.
2. Hubs must remove a nodes access to TTN as soon as
possible, when asked to by the N.A.
H. Nodes must abide by all of the N.A's administrative decisions.
I. Hubs may NOT allow nodes to relay TTN unless told by the N.A.
that the node has filled out the proper forms and has been
accepted into the net. The N.A. will inform a Hub of all
nodes accepted into the net, that will be using them for a Hub
via the Net Admin conference.
J. Hubs: to give a node status to import mail from people other
than his/herself, the account must have the "Net Status" flag
turned ON, otherwise, TriMail will not allow the node to
import messages from any of his/her users.
K. Recommendation: The user account used on a hub by a node should
not by the sysops name--it's best to use the BBS's name. I.E. my
account on a Hubs BBS for mail relays might be James Bond, and
Marks might be Lobster Buoy. Please o.k. this with your Hub
first.
L. All Hubs and nodes are asked to please delete any messages
containing "swear" words, or messages that are not deemed
appropriate. Let's all remember that kids will have access
to TTN on most boards carrying TTN.
M. Hubs and nodes must lock out any user from TTN that the N.A.
has found to have not lived up to TTN standards, such as
repetitive swearing or going against the grain or the network.
N. All nodes and Hubs must inform the N.A. of new idea for the
network. New conferences, ideas, etc---things to make the
network a better place is always welcomed.
5. Conferences
A. Required conferences - The following conferences are required
by all hubs and nodes
1. Net Admin
2. Net Chat
3. TriTel
B. Private Conferences
1. Net Admin conference is only to be seen and used by
TTN sysops, and NOT their users.
2. TT Support Board Conference is to ONLY be carried
by TriTel support boards, and is to only be seen
and used by the sysops. Hubs are allowed to carry
this conference for the sole purpose of passing it on
to a node that is a support board, unless of course
that hub is a support board.
C. Moderators of Conferences
1. Duties of Moderators
a. Enforce all Network Guidelines
b. Notify N.A. of any problem user in the Net
Admin conference
c. Keep messages on-topic
d. Do not allow users to "flame" others
e. Help users to the best of your ability
f. Keep your conference going--do not let it die
g. Control message quoting--don't allow
over-quoting to get out of control.
D. New conferences will be added from time to time, and old ones
dropped. It is your responsibility to keep track of them.
6. Messages
A. Private Mail
1. Pursuant to the Electronics Communications Privacy
Act of 1986, 18 USC 2510 et. seq., all BBS sysops and
users participating in TTN, MUST be aware that there
are NO facilities provided by TTN for sending or
receiving private mail. Although a message may be
marked as "private", users and sysops must be aware
that all sysops in TTN and users with high enough
security (sysops, cosysops, etc) will be able to read
said message.
2. It is the responsibility of every hub and node to
inform their users of 6.A.1's guidelines, preferably
by use of a bulletin.
7. Configuration and Maintainance
A. All TTN nodes and hubs taglines must begin with the following:
TTN:
1. Example:
TTN: James Bond's Hideaway (207) 942-6575 HST D/S
B. All network sysops must, on a regular basis, monitor the net
admin conference.
8. Network Rules
A. All TTN conferences are subject to the following guidelines,
which any user of any TTN conference must be made aware of,
and must follow.
1. No alias names--all users of TTN must user their
real name when entering a message into any TTN
conference.
2. No "Flaming"
a. Personal attacks, "flaming", will not be
tolerated in any TTN conference. Any user
found to be slandering others, being abusive,
discriminating a person because of their race,
creed, color, sexual preference, culture or
sex--or, if they are found to be just plain
arrogant can and may be locked out of TTN
under the terms in 4.L
3. No Illegal Activities
a. Any talk of ANY illegal activities in any TTN
conference may result in being locked out of
TTN under the terms in 4.L
4. No BBS Ads are allowed ANYWHERE.
a. Taglines are not considered BBS ads
5. No swearing in any TTN conference
9. Amendments and Modifications
A. It is the right of the N.A. to add new guidelines at any time
or to get rid of or modify any pre-existing guidelines. It is
every network sysops job to re-read the guidelines after
revisions have been made. If you disagree with any changes,
additions or deletions, that affect your decision to comply
with said changes, deletions or additions, then it is your duty
to inform the N.A. of your removal from TTN.
10. Fun
A. I hope these rules don't scare people away, as that is not my
intent. My intent with all of these rules is to have a place
where we can all have fun, and hopefully learn something from
one another.
11. Acknowledgments
A. I would like to acknowledge the fact that the Intelec Network
Guidelines written by Mr. Cliff Watkins, were the skeleton
behind how these rules were drawn up. Thanks Cliff!
<<END OF TEXT>>